No matter what Chronus provider I use, I get -18|-18 on the temperature range for the day. I don't get the same if I don't use Chronus as the weather provider for CM, so I'm guessing the problem is on Chronus' side...
Danny Baumann - 2016-05-04T05:34:05+0100 - Updated: 2016-05-04T05:37:05+0100
Last time I heard of this (when +Michael Bestas told me), the data transmitted to CM was good. Can you please post/send us the output of 'logcat -s CMWeatherService:V'? Additionally, what's your exact CM version and what provider do you use for the CM weather in Chronus?
This is using a custom mainline build from the 28th of April, and happens in all weather providers in Chronus I've tested (all that do not require an API key). Logcat available in:
I can't understand why CM team released unfinished stuff that doesn't work at all and nobody cares to fix it. I's not only the -18 -18 problem but also the weather in the status bar appears always in Fahreneit no matter what you choose in cLock or Chronus, the forecast usually is messed up and most of the time it never gets updated unless you update manually.
Danny Baumann - 2016-05-05T18:08:58+0100 - Updated: 2016-05-05T18:12:36+0100
+Spyros Barbatis A nightly not exactly counts as a release. The -18 problem likely is in Chronus, at least partially. +Marcos Marado The next release will have today's high/low filled out.
http://pastebin.com/3gGhQPu8
Looking at the log, I'm guessing the problem is on the fact that, for all providers, we have "Today's high temp: 0.0 Today's low temp: 0.0".
+Marcos Marado The next release will have today's high/low filled out.